AEMail 2.40/AEMail v2.40.iso/install.txt

Text File | 2001-03-22 | 37KB | 738 lines

                          INSTALLATION OF AEMAIL
                             (March 31, 2001)

The AEMail Install Script uses the Installer program first provided by
Commodore and later revised by Amiga Technologies.  You should use the
Install_AEMail script to install AEMail.  It is not recommended that you
attempt to install AEMail by hand since some actions are necessary through
the install script.  This is especially true if you are attempting to
install a registered version of AEMail!

    Installer and Installer project icon
    (c) Copyright 1995-96 Escom AG.  All Rights Reserved.
    Reproduced and distributed under license from Escom AG.

    INSTALLER SOFTWARE IS PROVIDED "AS-IS" AND SUBJECT TO CHANGE;
    NO WARRANTIES ARE MADE.  ALL USE IS AT YOUR OWN RISK.  NO LIABILITY
    OR RESPONSIBILITY IS ASSUMED.

Starting with Version 2.00 of AEMail, the Installation script was
completely re-written from previous versions.  You can now define multiple
users with the install script and use the install script to add or update
users as well as delete users (Version 2.30 and above).

The script was further modified for Version 2.20 to place additional edits
when naming configuration files and your mail directory.  The script also
installs the ClassAct classes required by AEMail if you are installing with
an OS prior to 3.5.  If you are installing to OS 3.5, it is not necessary
to install the ClassAct classes since they are built into the OS.

In OS versions prior to 3.5 you will be asked if you want to install
ClassAct.  It is not necessary to do this if you are already have ClassAct
installed on your system (either by a previous AEMail install or with
another program using ClassAct).

Other changes to the Version 2.20 installation script include:

    Changing RAM: to T: for saving temporary files.  On most Amigas, T: is
    in RAM:  However, in some low memory situations, a user may assign T:
    to a hard drive.  By changing RAM: to T:, users with low memory
    conditions can still install AEMail.

    If you have previously installed a version of AEMail 2.00 or above, you
    can bypass the "Configuring Users" portion of the script as long as you
    do not want to add to your users or update a user.

Further changes to the Version 2.30 installation script include:

    The ability to delete users.

    The installation script now asks what type of installation you are
    performing: a demo version, a previously registered version, or a new
    registered version.

Please read these instructions before attempting to install AEMail.

If you have the diskette version of AEMail, you will find that it is now a
two disk set.  Place Disk_1 in your drive to start the installation.  At
the appropriate time you will be asked to insert "AEMail_V2.30-Disk_2".

If you are installing from a version obtained over the Internet or from the
AEMail CD-ROM, you will not get this message.

To install AEMail simply double click on the "Install_AEMail icon".  The
install script provides two user levels that the user can choose:

    Intermediate    (control of configuration parameters only)
    Expert          (control of configuration and where files are placed)

See below for actions that are different between the two user levels.

The first thing that the Install script will ask is what type of
installation you are performing:

    A Demo Version
    A Previously Registered Version
    A New Registered Version

If you are installing a new registered version you will need a key code
which was provided when you purchased AEMail.  You will not be able to
continue with the installation if you can not provide the correct key code.
In this event you should re-install using the Demo Version and contact the
author at [e-mail] for further instructions.

Likewise, if you are installing a previously registered version, the
installion script will attempt to locate your registration information in a
file called .registration in you main AEMail program directory.  If your
previous installed version was prior to 2.00, it will look for the
registration file in AEMail:.registration.  If it can't be found you will
be instructed to install at the Demo Version level and to contact
[e-mail] for further instructions.  Before doing that, however,
execute your newly installed AEMail and see if it is a registered version.

The Install script then makes an attempt to determine which TCP/IP stack
that you have installed.  This controls which defaults will be taken.  The
way the install scripts knows which TCP/IP stacks are present is as follows
(you must have installed the particular stack before installing AEMail):

    AmiTCP:     This is controlled by the presence of the AmiTCP: assign
                statement and the presence of the AmiTCP:bin drawer.  The
                AmiTCP:  assignment and the AmiTCP:bin drawer were
                automatically created when you installed AmiTCP.


    Miami:      This is controlled by the presence of the Miami: assign
                statement.  When you installed Miami you should have let
                the install create the Miami: assign.  This was only
                available under later versions of Maimi.

                While the Miami:  assign is not an absolute requirement
                if you are using Miami, it is required if you intend
                to use the supplied "startnet.miami" script without
                modification.  This script locates Miami with Miami:Miami
                which depends on the Miami assign.  If the Miami assign is
                not present you would have to modify the script to use the
                full path name of where Miami is located.

    TermiteTCP: This is controlled by the presence of the TermiteTCP.prefs
                envronomental variable.  Also, if you want to pick up
                some of the other TermiteTCP variables, such as email
                address, you must have run TermiteTCP prior to installing
                AEMail (TermiteTCP does not have to be online, however).

The install script will ask you to verify which TCP/IP stack you are using.
A fourth alternative "Other" is provided if you have another TCP/IP stack
or you have not as yet installed your chosen stack software.

If you have multiple stacks installed, the initial stack selection is made
in this priority:

    Miami
    AmiTCP
    Termite-TCP

You can, of course, change this with the requester.

If you select the Intermediate user level, the following actions will be
taken:

    If you have previously installed AEMail with a version 1.10 or greater,
        the install script will determine where AEMail was previously
        installed from the ENV:AEMail_Dir environmental variable.

    If you have not previously installed AEMail or you are updating from
        an AEMail version prior to 1.10, the AEMail executable file will be
        placed in AmiTCP:bin if the AmiTCP stack was selected or, if one of
        the other stacks was selected, on the largest partition on your
        hard drive.

        Note: No special directory will be created if AmiTCP is
        selected, otherwise a directory called "AEMail" will be created
        for containing the AEMail executable.  When the installation
        script terminates it will tell you where it placed the AEMail
        executable.

        The reason that AEMail is placed in the AmiTCP:bin drawer if the
        AmiTCP:  assignment is present and you selected AmiTCP as your
        TCP/IP stack, is that the "startnet" and "stopnet" scripts for
        AmiTCP should be in the same directory that contains AEMail if they
        are to work without modification.  The AmiTCP installation places
        these scripts in the AmiTCP:bin drawer.

    For OS Versions prior to 3.5, the ClassAct classes will be normally
        installed to your SYS:Classes drawer.  You will be asked if you
        want the 020 optimized version of the classes.  If you are running
        on an 020 or greater processor, reply "yes".  With OS 3.5, the
        ClassAct classes will have been installed when the OS was
        installed.

    The documentation files that you want copied will be copied to a drawer
        called "documentation" in the drawer which contains the AEMail
        executable.

    A special ARexx documentation file (which is also part of the
        AEMail.doc and AEMail.guide files), is placed in a drawer called
        "ARexx" in the drawer which contains the AEMail executable.  This
        drawer will also contain some sample ARexx scripts.

    If you want the AEMail.readme file, it will be copied to the directory
        containing your AEMail executable.

    The ARexx scripts StartNet.Miami and StopNet.Miami will be copied to
        the directory containing your AEMail executable providing they are
        not already there.  This prevents copying over scripts that may
        have been previously modified.

    A handy registration form called "registration.form" will be available
        in your main AEMail directory.  It has an icon which, if you double
        click on it, will use the "PrintFiles" program in your SYS:Tools
        directory to print out the registration form.

    You will be asked how many users you want configured.  See the section
        below on Configuring Users to see what happens here.

    If you are updating a user, you can change their mail directory.
        However, if you are creating a new mail directory rather than using
        an existing one,  you will start out with a blank address book and
        empty standard folders.

    If you are running under AmigaDos 3.0 or greater, the supplied
        mailcap file will be copied to the mail directory for each user
        unless a mailcap file already exists in that user's mail directory.
        No mailcap file will be copied if one already exists in the user's
        mail directory or if you are using AmigaDos 2.1.

    An AEMAIL2: assign statement pointing to the drawer containing your
        AEMail executable will automatically be placed in your
        S:User-Startup file.

    An "ASSIGN C: SYS:REXXC ADD" will also be added to your s:User-Startup
        file to provide a path to your AREXX commands.

The following additional capabilities are provided when you install at the
Expert level:

    You will be able to choose which directory AEMail will be installed in.
        If you are installing AEMail for first time, this may be desireable
        rather than installing in the largest partition on your hard drive.
        The default directory that is selected will be the one that would
        have been selected under the Intermediate level.

    You will be able to choose which directory you wish to install your
        Documentation files in.  WARNING: for the Help function to properly
        work, the AEMail.guide file must be in the "documentation" drawer
        within the drawer which contains the AEMail executable.  You can
        change the location of the .guide file by using the "HELP=" Tool
        Type.  This must be done manually.  The Install script WILL NOT set
        this tool type.

    You will be able to choose which directory you wish to install your
        ARexx files in.  You might want to select the Rexx: directory for
        this so that the supplied ARexx scripts become immediately
        available.

    If you want a mailcap file other than the one provided, you can select
        where you want this file copied from.  If you want to use the
        alternate mailcap provided in the ARexx drawer for displaying HTML
        documents with your browser, you could specify the AEMail ARexx
        drawer for the source of the mailcap.

As noted above, the default drawer in which your documentation is placed is
a drawer called "Documentation" in the drawer containing your AEMail
executable.  This is different from versions prior to 1.50 where the
documentation files were placed in the same drawer as the AEMail
executable.  Documentation files located in the drawer containing your
AEMail executable WILL BE deleted by the installation script.  If you want
these retained you will have to re-name or save them yourself.

Towards the beginning of the script, after you have identified your TCP/IP
stack, the script will determine if you have already installed the current
version of AEMail.  If you have, you will be asked if you want to do a Full
Install or want to add, delete and/or update users.  If you just want to
add, delete or update users, you will go immediately to the "Configuring
Users" section described below.


                             Configuring Users
                             -----------------

You can set up multiple users of AEMail from the Install Script.  Each user
will be provided a Project Icon named as the user wishes.  This project
icon will point to the AEMail executable and will be created with certain
required Tool Types as "configuration" items.  The Project icons will be
created with the Install_AEMail script.

If you have previously installed a version of AEMail 2.00 or above, you
have already established your users.  In this situation all of the users
that have been previously defined will be displayed and you will be asked
if you want to "Add/Delete/Update Users" or "Accept Current Users".  If you
reply with "Accept Current Users", the user configuration section will be
bypassed.

If you have not installed AEMail previously or your previously installed
version is prior to 2.00, you will be asked how many users with different
email addresses you wish to configure AEMail for.  You must have at least
one user.  Certain questions will then be asked for each user so that
appropriate Project icons can be created with the appropriate Tool Types.

If you already have established users and replied "Add/Delete/Update Users"
you will first be asked if you want to delete any users.  If you do, your
existing users will be displayed and you can select the one you want to
delete.

The script will determine the Configuration file used by the user you want
deleted.  It will display a requester asking if you want to delete this
configuration file.  Unless you want to use this configuration file again,
you will want to delete it.

The script will then determine the Mail directory for the user you want
deleted.  Again it will ask if you want this mail directory deleted.  If
the mail directory is being used by another user you should not delete it.

After that user is deleted you will be asked if you want to delete
another user. If you don't, you will then be asked how many users you want
to add or update.  You can reply 0 to this message which will then bypass
establishing or changing any users.

As each user is processed you will get a message asking you to select the
name of the icon you want your user to have.  Since you can both create a
new user or update an existing user, you will be present with a list of
choices that looks like this:

    Create new icon
    name-of-previously-defined-user-1
    name-of-previously-defined-user-2
    ...........
    name-of-previously-defined-user-n

Only the names of previously defined users will appear in this list.  If
you select any of the users or the "Create new icon" entry you will get a
message that asks you to enter (or confirm) the name of the user (icon
name) that you want the user to have.  When you select "Create new icon" a
default name will be used that will be one of the following:

    AEMail_User_1
    AEMail_User_2
    AEMail_User_3
    ...........

    AEMail_User_n

You can change the name or use the one provided.  You will then be told if
the icon already exists or not and asked to confirm that this is the
correct name.  If you are editing a previously created icon, that icon, of
course will exist.  You will be given an opportunity to re-enter the name
if you decide it is wrong.

If you are updating from a previous version of AEMail (before 2.00), you
will already have a "Tool" icon for AEMail.  If you select "AEMail" as the
name, the "tool" icon will be turned into a Project icon for your primary
user and all existing Tool Types will be obtained as default values.  If
you choose to change the name of the icon, the "AEMail" tool icon will
remain.

WARNING:  Do not try to DELETE any icon called "AEMail" (tool or project)
AFTER you have installed AEMail using the workbench "Icons/Delete..."  menu
item.  This will delete the AEMail executable as well.  If you don't want
the "AEMail" icon it is best to delete it BEFORE installing AEMail or use
the delete function described above to delete the icon.

The required Tool Types that will be created for each user's Project icon
are:

    CONFIG=
    MAIL_DIR=
    PASSPROTECT=YES

The CONFIG= Tool Type points to the configuration file for that user.  This
configuration file must be unique for each user.  Under both install
options (Intermediate and Expert), a file requester will appear for you to
select the configuration file name.  If you are not updating an existing
user, this configuration file will not exist so you can enter whatever you
like (providing a file with the same name is not present).  You can select
any drawer, but either the drawer containing the AEMail executable or the
s:  directory are recommended.

If you start AEMail from the shell without any arguments, you will need to
name your primary user's configuration file aemail.cnfg in the s:
directory.

If you are doing a full install and you have a s:aemail.cnfg file, this
file will automatically be selected as your default configuration file for
your first user provided no configuration file was previous specified in
the "AEMail" Tool Types.  If you install at the "Expert" level, you will
be able to copy and/or rename this file to another location.

The MAIL_DIR= Tool Type is used to specify where your mail directory is
located.  In versions of AEMail prior to 2.00, the AEMail:  assign was used
to specify the mail directory location and the Tool Type was only used if
the mail directory differed from that.  This is no longer the case.  With
version 2.00 and above, the AEMail:  ASSIGN statement is no longer used,
the mail directory will always be specified by the MAIL_DIR= Tool Type.
After installing a user you can change their mail directory by either
changing this Tool Type or by running the Installation script again to
update this user.

If you are updating from a version of AEMail prior to 2.00, the AEMail
ASSIGN will be used to specify the default MAIL_DIR unless a MAIL_DIR=
Tool Type was previously specified in an updated icon.

For new users, you will be given an opportunity to accept the default as
the mail directory or specify a new mail directory location for each user.
The MAIL_DIR does not have to be unique to each user.  Two or more users
can share the same mail directory.  If the mail directory you specify is
not present, it will be created.

The PASSPROTECT=YES Tool Type is used to password protect the mail
directory for a particular user (only available for registered users).  You
will be told whether the mail file is currently password protected or not
and then be asked if you want to password protect the mail directory for
this particular user.  If the file was previously password protected, you
can turn that feature off by replying 'No'.  To continue password
protection you will have to reply 'yes'.  The password that is used to
password protect the directory is the same one that is used to access the
POP server by that particular user.

Previously an INTERLACE=YES Tool Type was used to specify the screen mode
that AEMail would initially open on.  This Tool Type is now obsolete.
AEMail will now initially open on whatever screen mode is set for your
Workbench screen.  After initially loading AEMail, you can change the
screen mode through the Configuration Edit screen, General page.

You will also be able to provide additional configuration data for each
user that will be stored in the Tool Types parameters of the AEMail Project
icon for that user.  If the user has an existing Configuration file, you
will be asked if you want to re-configure this user's data.  If you do, the
existing configuration file will be renamed with ".old" appended to it.  If
the user does not have an existing configuration file, you will be asked if
you want to configure now or wait until AEMail is first loaded.

Since you can change the configuration data from AEMail, the Configuration
file always takes precedence over the Tool Types.  The only exceptions to
this are the name of the configuration file (CONFIG=) and the name of the
mail directory (MAIL_DIR=).  That is why any existing configuration file
is renamed to avoid resetting the configuration data when AEMail is first
loaded.

Certain configuration parameters must be provided before AEMail will run.
These configuration parameters are provided either by Tool Types in the
AEMail icon or through a special Configuration Setup Window when you first
run AEMail and saved in the user's configuration file.

If these parameters are not provided by Tool Types (through the
installation script) or by an existing configuration file, the
Configuration Setup Window will be displayed upon the initial startup of
AEMail.  You can not proceed beyond this configuration setup until certain
required configuration parameters are provided.  The absolute minimum
configuration parameters that must be provided are:

    POP3 UserID
    Password
    Your email Address
    POP Server Name
    SMTP Server Name
    Domain Name
    Edit Call

For a full discussion on configuring AEMail, refer to the AEMail
documentation or guide files.

If you decide to configure using Tool Types, the installation script will
try to automatically configure certain items to default values.  These
include the switch for deleting mail from your POP Server once it has been
transferred to your Amiga and the switch for stripping duplicate messages.
The edit call will default to c:ed and will open the editor on the
Workbench.  Also, if you have your TCP/IP stack loaded (not necessarily
on-line), it will obtain certain default items from environmental variables
stored by the stack software.

The installation script will allow you to provide additional configuration
parameters as Tool Types in your AEMail icon or to change the default ones.

A POP Server name and a SMTP Server name must be provided.  However, if
they are missing AND, if the Domain Name has been specified, default
values will also be assigned to these items.  These default values will
prepend 'POP.' to the domain name for the POP server and 'SMTP.' to the
domain name for the SMTP Server as defaults.  Please note:  these may NOT
be correct for your POP and SMTP servers.  If they are not, you will have
to change these items with the installation script.  Some Internet Service
Providers use mail.  prepended to the domain server for both the POP and
SMTP servers.

If you have a problem understanding what should be entered with the
install, use the HELP function of the Install script.  Here is some of the
help information from the script:

  "The domain name is usually the part of your e-mail address that follows"
  "the '@' sign.  If something else is required by your Internet Provider,"
  "provide it here."

  "As an example, my email address is:"

        "[e-mail]"

  "The domain name for my Internet provider is therefor 'calweb.com'."


  "POP Server.  POP stands for 'Post Office Protocol' and your "
  "POP Server is the name assigned to the host computer that holds "
  "your Internet mail.  Normally this would be 'pop.' or 'mail.' "
  "prepended to your Domain name."

  "Consult your Internet provider if the POP Server is called "
  "something other than the above."


  "SMTP Server.  SMTP stands for 'Simple Mail Transfer Protocol' and "
  "your SMTP server is the name assigned to the host computer that "
  "sends your Internet mail.  Normally this would be 'smtp.' or 'mail.' "
  "prepended to your Domain name"

  "Consult your Internet provider if the SMTP Server is called "
  "something other than the above."


If you have installed and ran your TCP/IP stack before you installed
AEMail, the only configuration parameter you may have to provide is your
password.  If you are using TermiteTCP, the POP3 UserID and the SMTP Domain
Name are extracted from the email address that you gave TermiteTCP.  Other
stacks provide environmental variables to store this information.  If these
are not the correct values you will have to change them in either with the
Installation script or through the Identity page of the Configuration
Setup Window.

One of the things that is needed to run AEMail is an editor.  By default
AEMail will use the AmigaDOS editor, ed, which comes with all Amigas.
However, you can change this through the install to any editor that you
want provided that you have specified that you want to configure AEMail
when you do the install.

                           Other Considerations
                           --------------------

If you are using Miami as your TCP/IP software, special startnet.miami and
stopnet.miami scripts have been provided with the install of AEMail.  If
you select Miami as your TCP/IP stack and the Miami assign is present, the
install script assumes the Miami startnet and stopnet scripts should be
used.

If you are using AmiTCP, that software provides its own StartNet and
StopNet scripts.  They are usually in your AmiTCP:bin directory.  It is
recommended that you place AEMail in the same directory that contains these
AmiTCP StartNet and StopNet scripts, although this is not an absolute
requirement.  If AEMail is placed in a different directory, you might have
to modify these scripts to work properly.  If the directory containing your
StartNet or StopNet scripts is NOT the AmiTCP:bin directory or the scripts
have names different from "startnet" or "stopnet", you will have to change
the default values for the STARTNET and STOPNET tool types.  You can do
that with the installation script.

If you are using TermiteTCP, there are no Start Net or Stop Net scripts.

SPECIAL NOTE FOR MIAMI USERS:  In the TCP/IP Settings page on Miami, the
"Down when Offline" item should be checked and the settings SAVED.  If this
item is not checked, it will take AEMail 80 seconds to determine that Miami
is offline if Miami is loaded but not online.

WARNING:  If you are updating and you change the mail directory for a
specific user, you will lose all previous folder configuration data.  You
might also lose your registration information if you are a registered user.
In versions prior to 2.00, the registration information was stored in your
mail directory.  Version 2.00 and later stores it in the AEMail program
directory.  The installation script will attempt to copy this information
from the mail directory to the program directory.  If the installation
script can not find your old mail directory (usually by the AEMail:  assign
statement, you will need to copy this data yourself from your old
mail directory to the new mail directory.

The mail directory can start out empty.  The AEMail program will generate
any necessary configuration and support files required.  The mail directory
directory can be anywhere on any one of your hard drive partitions (or on a
floppy or other read/writable media); it does not have to be in any
specific directory; but it must be mounted when you execute AEMail.

As stated above, you will need a "mailcap" file if you want to display MIME
mail attachments.  A sample mailcap file is provided on the AEMail program
disk which uses MultiView to display audio, images, and video content types
provided that you have the appropriate datatypes loaded into your system.
This, of course, requires AmigaDos 3.0 or higher.  If you are using
AmigaDos 2.1, the mailcap file needs to be modified to reflect the display
programs that you want.  The installation script at the Expert level will
help you do this or you can do this with the "Viewer" page of the
Configuration Setup Window.

If you are running under AmigaDos 3.0 or higher, the installation script
will automatically move the supplied mailcap file to the mail directory
for each user unless a mailcap file already exists there or unless you
specified a different location for a pre-existing mailcap file (Expert
level only).

The mailcap file specifications are given in AEMail documentation and guide
files.

A special mailcap file is provided in the "ARexx" drawer to allow you to
display HTML attachments with your browser.  If you wish to use this
feature you will have to copy the mailcap file in the ARexx drawer to your
mail directory.  This can be done with the installation script at the
Expert level.  Read the html.readme file in the ARexx drawer for details of
this special mailcap file.

The mailcap file can also be created or edited online with AEMail through
the "Viewer" page of the Configuration Setup Window.

AEMail gets the current time zone from either the locale.prefs file that
is part of AmigaDos or the tz envronmental variable.  See "Handling of
Time Zones" below for further information on this.

When the installation script terminates it will store the directory in
which it placed AEMail in the Environmental variable "AEMail_dir".  It also
creates an assign statement in your User Startup for the AEMail program
directory called AEMail2:.  Starting with version 2.00 it will also store
the version number of the current AEMail in the environmental variable
"AEMail_Ver".  This facilitates updating to future releases of AEMail.
The version 1.30 and later installation scripts, at all installation
levels, will look for the AEMail_dir Environmental variable to try to
determine where to place AEMail.


                     HANDLING OF TIME ZONES IN AEMAIL
                     --------------------------------

AEMail will handle time zones in both full hour and half hour increments.
AEMail uses either the "tz" environmental variable, a special "aem_tz"
environomental variable, or the "locale.prefs" file that is part of
AmigaDos to determine your local time zone.  The "locale.prefs" file will
only allow for full hour time zone offsets.  You can use the "tz"
environmental variable for half hour time zones, but, if this variable is
used by other programs in your system it is suggested that you use the
"aem_tz" variable instead.

To set the time zone in the "locale.prefs" file, execute the Locale
program under your Prefs directory by double clicking on the Locale icon.
At the bottom right of the Locale Preferences window you will see a world
map with a white line through it that indicates the time zone that you are
in.  To change this, click on the country you are in.  The white line will
move to that position and the Time Zone heading at the top of the map will
reflect the time zone offset for your part of the world.  Then click on
the [Save] gadget at the bottom of the window.

Currently AEMail first looks for the environmental variables "aem_tz" or
"tz".  The format for "tz" is dictated by SAS_C and should be aaabbbccc
where aaa is the abbreviation for local standard time, bbb is the offset in
hours from GMT (-11 to 12) which is SUBTRACTED from GMT to get the local
standard time.  ccc is the abbreviation for local daylight savings time or
"summer time" (in the United Kingdom or Europe).  If the time zone has
daylight savings time this should be present even if daylight savings time
is not currently in effect (contrary to the specification for "Tz" for the
SAS-C compiler).  AEMail automatically determines when DST or "Summer Time"
is in effect.

AEMail also recognizes an alternate form of "tz" where aaa and ccc can be
abreviations longer than 3 characters.  This is desireable in some European
countries.  AEMail will also recognize time zones in increments of one half
hour.  To specify an half hour time zone, specify it as + or - hhmm.  As an
example:  +230 would specify a time zone in which 2 and a half hours are
SUBTRACTED from GMT.

You can enter the above with the "tz" environmental variable, but since
this variable might be used with other programs in it's strict sense, an
alternate environmental variable has been provided called "aem_tz".

If "aem_tz" is present it will take precedence over "tz".

If the "tz" or "aem_tz" environmental variables are not present,
the system then attempts to get the time zone offset from the
"locale.prefs" file.  Only the time zone offset is present in this
file.  The abbreviations for local standard time and daylight savings
time are obtained from a table that is by no means complete.  Only the
time zone abbreviations for the United States, Canada, and the United
Kingdom are contained in this table, so one of the environmental variables
is preferred.

if neither the "tz" nor "aem_tz" environmental variables nor the
"locale.prefs" file are present, the system defaults to CST with an
offset of 6.

NOTE: the standard header in an email message has the time zone offset sign
reversed from that of the "locale.prefs" and the environmental variables.
AEMail automatically makes this reversal, so the offset should be set to
positive for US time zones and negative for European time zones.  They
will appear as negative (for US) and positive (for Europe) in the Date:
header.

You can set the "tz" or the "aem_tz" environmental variables by using
the SETENV AmigaDos Command.  This must be done from the shell.  The
syntax to use is as follows:

    SETENV tz aaabbbccc                            (for tz) and
    SETENV aem_tz aaaaaaaaabbbbbccccccccc          (for aem_tz)

aaa, your local time zone abbreviation must always be present.  If you
don't know your abbreviation (or don't want it in the header), use "xxx".
If AEMail sees xxx it will assume that no abbreviation is present and
it will be left off the Date: header

bbb is the time offset in hours from GMT.  Plus indicates that you are west
of GMT and minus indicates that you are east of GMT.  Acceptable values are
-12 to 24.  If you want to specify a half our time zone it can be entered
as hhmm.  If AEMail sees a value of 30 or above it assumes that a half hour
increment is being used.  In this case -1200 to 2400 are acceptable.

If your time zone observes daylight savings time, ccc is the abbreviation to
use for daylight savings time.  If ccc is not present, no adjustment will be
made during the times of the year that daylight savings time is observed.

The result of the SETENV command is only in effect while your computer is on.
If you want to make the "tz"or "aem_tz"  environmental variables always
present enter the one of the following AmigaDOS command after the SETENV
command:

    COPY ENV:tz ENVARC:tz                          (or)
    COPY ENV:aem_tz ENVARC:aem_tz

Using the "tz" or "aem_tz" environmental variables gives you more control
over which abbreviations will be used for your time zone.  However, the
locale.prefs file may be more useful for those that prefer the "point and
click" method of doing things.  To set the correct time zone for
locale.prefs, enter the Locale editor in your Prefs drawer.  You will
see a time zone map with which you can move the white strip indicating
the time zone on the map.  Click either to the left or right of the strip
to move the strip.  The correct time zone offset for standard time will be
shown at the top of the map.

Since the locale.prefs does not have any abbreviations, AEMail makes certain
assumptions as to what the abbreviation should be.  These assumptions are as
follows:

Time Zone Name           Standard    DST  -----------Time Zone-----------
                         Time             (in "locale")  (in email Date:)

Greenwich Mean Time      GMT*        BST       0              +0000

Atlantic Time            AST         ADT       4              -0400
Eastern Time (US)        EST         EDT       5              -0500
Central Time (US)        CST         CDT       6              -0600
Mountain Time (US)       MST         MDT       7              -0700
Pacific Time (US)        PST         PDT       8              -0800
Yukon Time               YST         YDT       9              -0900
Hawaiian Time            HST         ---      10              -1000

International Date Line  IDL         ---      12              -1200

--- indicates this time zone does not observe DST

*Note:  GMT (Greenwich Mean Time) is also known as UTC or Universal
Time Coordinated.

If you want to use a different abbreviation or control whether DST is used
or not, you should use the "tz" or "aem_tz" environmental variable.

DST in the United States and Canada begins on the first Sunday in
April.

"Summer Time" in the United Kingdom and Europe begins on the last
Sunday in March.

Both DST and "Summer Time" end on the last Sunday in October.